TEIs Rel-18
R1-2302385 Rel-18 TEI proposal
on HARQ multiplexing on PUSCH Huawei, HiSilicon, Ericsson, China
Unicom
R1-2302400 RAN1 TEI proposals
for Release 18 Nokia, Nokia Shanghai Bell
R1-2302513 Rel-18 TEI proposals vivo
R1-2302576 TEI on the
introduction of a UE capability with up to 6-layer DL MIMO OPPO
R1-2302762 On PUSCH repetition
type A scheduled by DCI format 0-0 with CRC scrambled by C-RNTI ZTE, China
Telecom, Sanechips
R1-2302973 Rel-18 TEI on
pathloss RS for Type 1 CG PUSCH xiaomi
R1-2303620 Rel-18 RAN1 TEI
proposals Qualcomm Incorporated
R1-2303851 Proposals for Rel-18
TEI Ericsson, Verizon, Qualcomm
[112bis-e-R18-TEIs-01] – Shinya (NTT
DOCOMO)
Email discussion on Rel-18 TEI proposals
April 26th
-
Check points: April 21,
April 26
R1-2304077 Summary #1 on
Rel-18 TEIs Moderator (NTT DOCOMO, INC.)
From April 20th GTW session,
Following proposals are considered:
·
TEI proposal #10: Enhancement for HARQ
multiplexing on PUSCH
o
Continue discussion to address the concern
from ZTE
·
TEI proposal #1: Multi-PxSCH scheduling with
single DCI
o
Continue discussion and check the view of
opponents (CATT, MediaTek)
·
TEI proposal #4: PUSCH repetition type A for
a PUSCH scheduled by DCI format 0_0 with CRC scrambled by C-RNTI
o
No more discussion in this meeting
·
TEI proposal #3: PUSCH antenna switching
o
No more discussion in this meeting
TEI proposal #10
The restriction on scheduling PDSCH after UL grant should be removed
for the case of PUSCH with repetitions
Ø An RRC parameter to configure the function of scheduling PDSCH after
a UL DCI format and multiplexing associated HARQ on the PUSCH scheduled by the
DCI format can be introduced in Rel-18.
Ø Note: When the restriction
on scheduling PDSCH after UL grant is released for PUSCH with repetition case, UE generates
type1/3 HARQ-ACK CB according to the existing specification.
Ø Note: Above proposal applies to type HARQ-ACK 1/3
CB. FFS: type-2 HARQ-ACK CB
Ø Note, the PUSCH with
repetitions can be scheduled/configured by gNB.
Ø FFS: case
of PUSCH without repetitions
Ø This feature is subject to UE
capability.
Companies with concerns: ZTE
TEI proposal #1
Introduce UE feature(s) for multi-PUSCH
scheduling with single DCI 0_1 for non-contiguous slots in FR1 for all defined
SCSs
·
Note: there is no RAN1
impact
Introduce UE feature(s) for multi-PDSCH
scheduling with single DCI 1_1 for contiguous/non-contiguous slots in FR1 for
all defined SCSs
·
Note: there is no RAN1
impact.
Companies with concerns: CATT, MTK
R1-2304108 Summary #2 on
Rel-18 TEIs Moderator (NTT DOCOMO, INC.)
From April 24th GTW session,
Agreement (proposal #1)
Introduce UE feature(s) for multi-PUSCH
scheduling with single DCI 0_1 for non-contiguous slots in FR1 for all defined
SCSs
·
Note: there is no RAN1
impact
TEI proposal #13
Rel-18 TEI proposal on pathloss RS for Type 1 CG-PUSCH is agreed. Relevant TP for clause
7.1.1 in TS 38.213 is endorsed.
|
7.1.1
UE behaviour
<Unchanged
parts are omitted>
- For a PUSCH transmission
configured by ConfiguredGrantConfig, if rrc-ConfiguredUplinkGrant
is included in ConfiguredGrantConfig,
-
if the UE is
provided enablePL-RS-UpdateForPUSCH-SRS, the UE determines a RS resource
index  from
the value of PUSCH-PathlossReferenceRS-Id that is mapped to the sri-PUSCH-PowerControlId
indicated by the srs-ResourceIndicator value included in rrc-ConfiguredUplinkGrant
-
if the UE is not
provided enablePL-RS-UpdateForPUSCH-SRS, a RS
resource index  is
provided by a value of pathlossReferenceIndex included
in rrc-ConfiguredUplinkGrant where the RS resource
is either on serving cell  or,
if provided, on a serving cell indicated by a value of pathlossReferenceLinking
<Unchanged
parts are omitted>
|
From email decision posted on April 26th,
no consensus to endorse proposals #10 and #13.
Final summary in R1-2304223.